Just thinking about this, I'm wondering if we need to put a switch in based on the version of sensu requested unless you're planning on adding (at least) some of the older versions into your new repository.

I made these changes independently and found that puppet runs fail due to the new repository key not being added. I had to add some version check hackery to add the key to clients that aren't running 0.21.0 in order to get the key added.

Would it not make more sense to add all the old packages to repositories.sensuapp.org and point repo.sensuapp.org to where the new packages are hosted?

How is this still not merged?

@taik0 There appear to be open questions about the PR and backwards compability. Until those are resolved we're not going to merge the PR. Would welcome your input or addition to the PR! Thanks!

Ping @portertech re old versions.

@jamtur01 Ops, I see, didn't know that @portertech was a Sensu contributor.
So we are waiting to see if Sensu add the old packages to the new repo?
If they didn't do it, should I create a PR like @jlambert121 said configuring the old or the new depending on the version?

It looks like this PR needs the apt key updated as well, the fingerprint doesn't match the key used by the APT repository. Same problem as Yelp/puppet-uchiwa#62

Why not merge those repos as @roobert suggested? If I use current puppet module I get 4 months old version..

Updated the key to match Yelp/puppet-uchiwa#62

Ping @jlambert121

ping @jlambert121 ;)